Example project — Frond is not real.

Authored demo content for a fictional plant-care app, rendered by the same parsers and held to the same invariants as a real project's dashboard. This is the system in use, three months in.

docs/strategy/Care Model.mdCommitmentsactive2026-06-30Read when: before any work that changes a schedule, a reminder, or a confidence band

The Care Model

How Frond turns a plant plus a room into a watering interval. This is the doc every scheduling change has to argue against.

The three inputs

Species baseline. A licensed interval range, treated as a starting hypothesis rather than a fact.

Measured light. The room survey's band. This is the input that moves the number most, and the reason the survey shipped before reminders.

Pot and soil volume. Asked once, at plant creation. Small pots dry faster than any light adjustment can account for.

Uncertainty widens, never narrows

Where two inputs disagree, the interval band gets wider, not averaged. A wide band shows the user a range and asks them to check the soil, which is the honest answer.

What we deliberately do not model

Humidity, drafts, and season beyond a coarse summer/winter shift. Each would need a sensor we do not have or a question we are not willing to ask.